-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
do not allow inference in predicate_must_hold
(alternative approach)
#110100
do not allow inference in predicate_must_hold
(alternative approach)
#110100
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 0779b6620d33449d376a8b437caa060a364cd6e0 with merge dc2620d92af7fa332c95a7cd35393bf9510ac125... |
This comment has been minimized.
This comment has been minimized.
0779b66
to
4230620
Compare
@bors try |
⌛ Trying commit 4230620b72959d6be0cfe37de66d63cc571c5ad2 with merge f1594433169cca61dd6137e11b86ca894968fb2f... |
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
@craterbot check |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
Finished benchmarking commit (f1594433169cca61dd6137e11b86ca894968fb2f): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
🎉 Experiment
|
4230620
to
a15ca71
Compare
🔔 This is now entering its final comment period, as per the review above. 🔔 |
☔ The latest upstream changes (presumably #109732) made this pull request unmergeable. Please resolve the merge conflicts. |
a15ca71
to
c06e611
Compare
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
@bors r+ rollup=never |
☀️ Test successful - checks-actions |
Finished benchmarking commit (19ca569): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 641.663s -> 641.09s (-0.09%) |
Correct me if I'm wrong, but the perf hit looks expected, and since this PR looks like this is a correctness fix, it's deemed acceptable. |
Hey @compiler-errors and @lcnr , based on https://github.com/rust-lang/rust/pull/110100/files#diff-cacebb74c41e0865cc830e29d5404a2c69a9901c37e4f1b579eb383ed71b12c8 going from run-pass to compile-fail, this seems like it could be a breaking change, ...
(Update: The things I was asking for were on this PR, just hidden under the fold.) |
I am going to assume from context (namely the 👍 from @lcnr ) that this is indeed a correctness fix of some form, and therefore the perf regression is expected and acceptable. @rustbot label: +perf-regression-triaged |
@pnkfelix look in the comments above for crater, FCP, and description of changes. |
sorry for the noise! |
See the FCP description for more info, but tl;dr is that we should not return
EvaluatedToOkModuloRegions
if an obligation may hold only with some choice of inference vars being constrained.Attempts to solve this in the approach laid out by lcnr here: #109558 (comment), rather than by eagerly replacing infer vars with placeholders which is a bit too restrictive.
r? @ghost